HPAVC

home *** CD-ROM | disk | FTP | other *** search

/ HPAVC / HPAVC CD-ROM.iso / pc / BLAB_064.ZIP / BOOMLAB.DOC < prev next >

Wrap

Text File | 1995-07-23 | 46.3 KB | 947 lines

@X3F ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄@X30 @X38 ■ ▀ ▄▀▄█▄▀█▄████▌▌@X70 -:- BOOMLAB HELP -:- @X38▐▐████▄█▀▄█▄▀▄ ▀ ■@X30 @X38 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀@X30 @X3F The Complete Upload Processor for PCBoard @X3F Coded by Gene Layton (BOOMER) ┌─────────────────────────────────┐ │░ 1. INTRODUCTION ░░░░░░░░░░░░░░░│ └─────────────────────────────────┘ BOOMLAB is a full featured upload processor. It comes as a standalone version for PCBoard and other BBS's and is also used in local mode with the BOOMER Utils for FORUM hacks, and PFED file manager packages. Therefore these docs will apply to all. REGISTRATION: ──────────── This program is SHAREWARE. It is not crippled in any way. The fee to register this product is $10.00 U.S. funds, or only $5.00 if your also registering PFED. ($20.00 for both) All funds must be U.S. Dollars, send cash at YOUR OWN RISK!!! Complete the included REGISTER.FRM BOOMER & remit fee by check or money order, P.O. BOX 560284 payable to GENE LAYTON. Mail to: ORLANDO, FL. 32856-0284 SUPPORT: ─────── Currently the only way to reach the author is at the LCS support BBS (4o7)898-4148. (USR 28.8k) To ask questions, reports bugs, or make suggestions, leave E-mail for 'BOOMER' or the SYSOP. Registered users receive top priority. New versions of PFED and BOOMLAB are also available online. DISCLAIMER: ────────── This software is provided without any guarantee or warranty either expressed or implied. I will not be held responsible for ANY damages that may result in the use of this program. "ANY" means if you install it, run it, and it eats your programs that you've been working on forever without a backup... IT'S NOT MY FAULT!!! PFED, BOOMLAB and this document are Copyright (C) 1994-95 by LCS Inc., all rights reserved. ┌─────────────────────────────────┐ │░ 2. BOOMLAB FEATURES ░░░░░░░░░░░│ └─────────────────────────────────┘ BOOMLAB supports over 50 different options for testing and processing uploaded files. Run BOOMLAB setup program (BSETUP.EXE) to configure these options. Following is a brief summary of options: ■ ARCHIVE PROCESSING: ∙ Supports ARC, PAK, ZIP, ARJ, LHZ, and .RAR archive formats. ∙ Test archive and embedded archive(s) integrity. ∙ REPACK files from ARC, ARJ, PAK, LHZ, RAR or ALL to ZIP format. ∙ Support for External Archive Converters, repack to any format. ∙ Add new comment for ZIP's and ARJ's. Customize with macros. ∙ Strip -AV protection from .ZIP's. (Requires STRIPAV.EXE) ∙ Define a list of filenames to delete. ∙ To detect and delete random BBS ads add CRC values using the archive viewer or define a list of text strings to search for. ∙ Define a list of files to add to archive. ∙ Age constraint can be entered using # days. ∙ Can age test file 5 different ways: NEW/OLD/DIZ/AVG/MOST. ∙ Define a list of files to EXCLUDE from date checking. ∙ All international date formats supported. ■ DESCRIPTION FILES: ∙ Supports FILE_ID.DIZ, DESC.SDI, & DISK.ID description files. ∙ Adds BBS Pass-thru text to DIZ's. ∙ 'Smart' word-wrapping. Turns off if ANSi, PCB, or Box graphics. ∙ Strip all high-bit ASCII characters. ∙ Amiga/console descriptions detected and converted. ∙ Define a list of text used to strip lines from DIZ text. ∙ Define a list of text strings to replace in DIZ text. ∙ Remove all blank lines from DIZ text. ∙ Remove PCBoard and Wildcat @ color codes from DIZ. ∙ Convert MCI | color codes to PCB @X codes or Strip them from DIZ. ∙ Define a list of characters to translate in DIZ text. ∙ Define a macro text file with file stats info to add to desc. ∙ Supports ULBY.PPE's ULBY.DAT which allows uploader 'signatures'. ∙ Define your own Failed BOOMLAB file description using 'DESCFAIL.MSG'. ■ VIRUS SCANNING: ∙ 6 different virus scanners supported. Any # of scanners even all 6 can be used in a multiple scanner configuration. ∙ Virus scan ALL files or only executables. ∙ RAM-drive can be used for FAST virus scanning. ∙ Embedded files are fully testing. ∙ Will log and report actual virus name if detected. ∙ Files can be scanned using Heuristic Analysis if available. ∙ Can skip files with specified extensions. (Ex: .VIR) ■ MISC. FEATURES: ∙ 32 different macros that can be used to personalize BBS Ads, ZIP comments, file descriptions, and 'Uploaded by' text string. ∙ Supports GIFLITE GIF Compressor from White River Software. ∙ Supports GIFTEST GIF Tester by Dave Navarro. ∙ Support for External Dupe Checkers ULP and ZDCS. ∙ Detailed processing log. ■ UPLOAD PROCESSING OPTIONS: (PCB ONLY) ∙ Display progress to users. ∙ 'LOCAL' command line switch that accepts wildcards for filenames. ∙ Reject uploaded archive formats by extension. Ex: .HYP.SQZ.ZOO ∙ Reject uploads found in blacklist, wildcards ok. ∙ Define a privileged user list. If files fail user still gets credit. ∙ Delete upload if user doesn't enter a description and a description file (FILE_ID.DIZ etc...) wasn't found in archive. ∙ Replace PCBoard's 'Carrier Lost ...' message with your own text. ∙ Supports the PCBALIAS PSA if used in PCBoard. ∙ Includes FILESYS.PPE to handle failed uploads. Can E-mail sysop and/or user, Delete, or NUKE failed files automatically! ┌─────────────────────────────────┐ │░ 3. INSTALLATION ░░░░░░░░░░░░░░░│ └─────────────────────────────────┘ BOOMLAB should be unzipped into it's own directory. You can install it to the PFED/FED directory if you wish. Run BSETUP.EXE to configure. Add the BOOMLAB command line to your board's upload batch file. (See MODES/BATCH FILE SETUP) If running under PCBoard make sure 'Swap Out During Shell' is enabled. Run PCBSETUP.EXE and select Option G (Configuration Options), then Option D. (Configuration Switches) Set 'Swap Out During Shell' to 'Y'. It will give you about 200K more memory. EXTERNAL PROGRAMS REQUIRED: ────────────────────────── BOOMLAB supports processing of the following archives: ARC, ARJ, LHZ, PAK, RAR, and ZIP's. Unless you have the setup to reject the format you will need following programs in the same directory as BOOMLAB or in the path. .ARC - PKPAK.EXE, PKUNPAK.EXE .ARJ - ARJ.EXE .LHA/.LZH - LHA.EXE, if using LHARC or LH rename it to LHA.EXE .PAK - PAK.EXE .RAR - RAR.EXE .ZIP - PKZIP.EXE, PKUNZIP.EXE STRIPAV.EXE (optional) .GIF - GIFTEST.EXE, GIFLITE.EXE (both optional) ┌─────────────────────────────────┐ │░ 4. MODES/BATCH FILE SETUP ░░░░░│ └─────────────────────────────────┘ The following modes are avaliable in BOOMLAB.EXE standalone version: UPLOAD - PCBoard upload processing. ATTACH - PCBoard testing for files ATTACHed to mail. TEST - PCBoard online test mode, callers can test archive integrity only and display results. LOCAL - PCBoard local command line processing. NONPCB - Partial upload processing for NON-PCBoard BBS's. PCBOARD BATCH FILE MODES: (PCBTEST.BAT) ──────────────────────── For BOOMLAB to test uploads to your BBS it needs to be added to your your PCBTEST.BAT file. Add the line as listed below, all you should change is BOOMLAB's full path and filename (#1), and the full path to where the BOOMLAB config and batch files are (#2). If using with a multi-node BBS you should set the %PCBDIR% variable in each node's BOARD.BAT file. (Ex: SET PCBDIR=D:\PCB\NODE1\) Single line BBS's should replace all references to %PCDIR% below with the PCB BBS path. (Ex: C:\PCB\) Syntax: BOOMLAB [CFG PATH] [%2-MODE] [%1-ARCHIVE] [%3-TEXT OUT] [BBS PATH] MULTI-NODE BATCH LINE EXAMPLE: (DON'T CHANGE 3-5) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (1) (2) (3)(4)(5) (6) C:\PFED\BOOMLAB C:\PFED\ %2 %1 %3 %PCBDIR% │ │ │ │ │ └── Passes the node directory │ │ │ │ │ Ex: D:\PCB\NODE1 BOOMLAB's full ┘ │ │ │ │ path and filename │ │ │ └── %3 - PCB Passes the output file │ │ └───── %1 - PCB Passes the filename │ │ Path of BOOMLAB.CFG ─┘ └───── %2 Passes PCB processing mode: & BOOMSCAN.BAT and 'UPLOAD' - test BBS uploads all macro text files 'ATTACH' - testing attached files 'TEST' - PCB online test mode MULTI-NODE PCBTEST.BAT EXAMPLE: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @echo off rem *** DELETE OLD TEMPORARY FILES *** if exist %pcbdir%\pcbpass.txt DEL %pcbdir%\pcbpass.txt >nul if exist %pcbdir%\pcbfail.txt DEL %pcbdir%\pcbfail.txt >nul if "%1"=="" goto ENDTEST if "%2"=="" goto ENDTEST if "%3"=="" goto ENDTEST if not exist %1 goto ENDTEST rem *** BOOMLAB COMMAND LINE *** d:\pfed\boomlab d:\pfed\ %2 %1 %3 %PCBDIR% :ENDTEST ECHO ■ Returning to PCBoard CD %pcbdir% LOCAL COMMAND LINE MODE: ─────────────────────── Files for PCBoard can also be processed via the DOS command line. Some uses for this may be as a basic FILE TOSSER for Echos or to manually add files to PCB DIR's. Syntax: BOOMLAB [CONFIG PATH] [MODE] [ARCHIVE] [DIR DESC FILE] [PATH TO MOVE FILES (Optional)] COMMAND LINE EXAMPLE: ~~~~~~~~~~~~~~~~~~~~ C:\PFED\ LOCAL D:\HOLD\*.* D:\PCB\MAIN\PUBLIC D:\UPLOADS │ │ │ │ │ │ │ │ │ │ Path to ───┘ │ │ │ Path to move files ─┘ BOOMLAB.CFG │ │ │ to after processing │ │ │ [OPTIONAL] 'LOCAL' Mode ───┘ │ │ │ └── PCB DIR text file to Path & name of file(s) ─┘ add descriptions to to process (wildcards ok) NON-PCBOARD MODE: ──────────────── For NON-PCBoard BBS's, BOOMLAB can be added to your BBS's upload batch file to perform some of the basic BOOMLAB functions such as add and delete BBS ad files. It performs only those function's in setup page #1, options 14, 15, 16, 17, 18, & 19. (*) Syntax: BOOMLAB [CONFIG PATH] [MODE] [ARCHIVE] BATCH EXAMPLE: ~~~~~~~~~~~~~~ (1) (2) (3) (4) C:\PFED\BOOMLAB C:\PFED\ NONPCB %1.%2 │ │ │ │ BOOMLAB's full ┘ │ │ │ path and filename │ │ │ │ │ └── Archive filename (varies) │ │ Path of BOOMLAB.CFG ─┘ └────── Must Use 'NONPCB' for all macro text files all NON-PCB BBS's ┌─────────────────────────────────┐ │░ 5. ARCHIVE PROCESSING ░░░░░░░░░│ └─────────────────────────────────┘ Options are listed below in order of their appearance on PAGE #1 of the BOOMLAB configuration program. (BSETUP.EXE) 1.) Your country's date format: (0-2) - Must be correctly set for age testing to work properly. 0 - U.S. Style MM-DD-YY <Default> 1 - European Style DD-MM-YY 2 - Japanese Style YY-MM-DD 2.) Fail files older than # days: (0=Off) - Use option #3 to specify which type of age checking to use. 3.) Type of age checking to use: (5 Types) NEW - Use date of NEWest file. <Default> OLD - Use date of OLDest file. (Dangerous!) DIZ - Use date of FILE_ID.DIZ AVG - Use Average date of files. MOST - Pass file if MOST files pass age test. If you would like to exempt certain files from date checking, then create a text file named 'EXCLUDE' in the same path the the BOOMLAB config is in. One file per line. Wildcards ok. Example: PK*.EXE ARJ.* FILE_ID.DIZ 4.) Rejected archive formats: Enter all formats you don't accept on your BBS. A period must precede extension(s). Ex: .ARC.HYP.PAK.SQZ.UCZ.ZOO 5.) Test archive integrity: <Y/N> - Tests the archive for CRC or other errors. Embedded archives are extracted and tested ONLY if virus scanning is enabled. 6.) Strip ZIP -AV protection: <Y/N> - If 'Y' then STRIPAV.EXE must be in the path. 7.) REPACK .ARC.ARJ.LZH.PAK.RAR or ALL: Leave blank to disable. Use 'ALL' or list all formats to repack by entering their extensions, preceded by a period. Ex: .ARC.ARJ.LZH .ARC = Convert to ARC format .ARJ = Convert to ARJ format .LZH = Convert to LZH format .PAK = Convert to PAK format .RAR = Convert to RAR format ALL = Convert ALL formats to ZIP NONE = Disable feature This option and the option #8)TO applies to both internal converter and external converters. If using the internal converter note that it only converts to ZIP format and internal paths are not supported. If using BOOMLAB upload processor for PCBoard you must be using version 15.1 or higher for PCBoard to recognize the new filename. 8.) REPACK TO: Format archive is to be converted TO. The internal converter only supports .ZIP, do not use any other extension. If using an external converter enter the extension of the new format you are converting to, OR the upload will show off-line. 9.) External Archive Converter Parameters: Leave blank to disable or to use the internal repacker. The internal converter only converts archives to .ZIP and does not convert recursive paths. If you need to use a full archive converter enter the command line with any switches here. The macro |fn can be used for filename if it is omitted it will be added to the end of the command line. Converters that should work are AC, STEALTH, SHEZ, and ZZAP. I've tested the following converters: STEALTH v5.0 (c) David Smith Ex: C:\STEALTH\STEALTH |fn AC v3.11 (c) Donald M. Langhorne Ex: C:\AC\AC /z |fn 10.) Uncompressed extensions to compress: Enter any uncompressed extensions you would like compressed to ZIP. Enter each .EXT (include period) Ex: .COM.EXE.ANS.TXT.DOC 11.) External duplicate file checking system: (Dupe Checker) A dupe checker will scan the contents of an archive and fail a file if a percentage of the files match a previous upload. Keeps people from renaming files to get credit. GiFs and executable files will also be failed if they match a previous upload. There are two external checkers supported, ZDCS and ULP both by Stacey Smith. Both are fast and do a good job, I personally prefer ZDCS since it was designed as a add-on to upload processors. To use ULP create a ULP config file named BOOMULP.CFG and turn off all it's other features. 12.) Path to the duplicate checker: Enter on the path, do NOT include the filename. (Ex: D:\ZDCS\) 13.) Dupe check local uploads: <Y/N> - If you re-process files a lot in local mode you should leave this off. * 14.) LIST of files (BBS ads) to be added to archive: Leave blank to disable. NOTE: This is a filelist not THE actual file to add. Create a text list of files to add, one per line. (Ex: ADDFILES.LST) Make sure to add the full path for each file in the list. Ex: D:\PFED\STUPID.AD D:\PCB\BBS\MORON.AD * 15.) LIST of files (BBS ads) to delete from archive: Leave blank to disable. List should consist of 1 filename per line. Path's and wildcards can also be included. In addition to filenames CRC values can be added to find those ever-changing random ad files. (Ex: = CRC:A07B3A31) The archive viewer in FED/PFED is helpful with adding filenames & CRC values to the delete filelist. * 16.) Text keyword list to ZAP random BBS ads: List should consist of one BBS ad keyword string per line. Can be any length, is not case sensitive, and can contain Hi-bit ASCII characters. BOOMLAB will extract all text files and scan each for any matching text! A sample 'BBSADTXT' has been included with this package. This should be lethal to most random BBS adders, it takes a little longer to process but worth it. Currently only ZIPs are scanned. * 17.) List of files never to be ZAPPED: When using the text search in option #16 a file may be detected (Ex: Group .NFO file) that you may not want to delete. This list lets the user specify files that are never to be deleted. List should consist of one filename per line and is not case sensitive. * 18.) Filename of text file to translate: Any macro codes in this text file will be translated and the to an output file with same filename but with a .CMT extension. The new file can be listed in the list of files to add or whatever. (Option #14) * 19.) Comment text file to add to ZIP or ARJ archives: (Blank = Off) You can also use BOOMLAB's macros anywhere in the comment text to customize the comments. A sample comment file 'ZIPCMT.TXT' is included in the BOOMLAB package. ┌─────────────────────────────────┐ │░ 6. FILE DESCRIPTIONS ░░░░░░░░░░│ └─────────────────────────────────┘ Options are listed below in order of their appearance on PAGE #2 of the BOOMLAB configuration program. (BSETUP.EXE) 1.) Maximum # of description lines: <1-60 lines> - This is the maximum length of a description including file stat macros, uploaded by, pass-thru text and added blank line. 2.) Extract and use description file: <Y/N> - This file will replace any user description entry. Supported description files are: FILE_ID.DIZ, DESC.SDI, and DISK.ID. 3.) Enable 'smart' text word-wrapping: <Y/N> - If enabled BOOMLAB will word-wrap text descriptions. The 'smart' indicates if any ANSi, PCBoard, or ASC Hi-Bit graphics are detected then word-wrapping is not done. 4.) Strip all high-bit ASC characters: <Y/N> - If enabled all ASCII characters higher that 127 will be removed. 5.) Strip PCBoard/Wildcat @ color codes: <Y/N> - If enabled all @X## and @##@ color codes will be stripped from DIZ's. 6.) MCI color codes <S>trip, <C>onvert: <S/C/N> - Leave blank or 'N' to disable option. If <S> all pipe color codes such as |15 will be stripped from DIZ's. <C> converts all MCI color codes to PCBoard's @X color codes. 7.) Strip ALL blank lines: <Y/N> - Will strip any and all blank lines from a description file. 8.) List of text lines to REMOVE from DIZ text: Leave blank to disable. One entry per line. Text is not case-sensitive. If the text is found in the DIZ text the line is completely removed. It will strip those annoying 'pass-thru' or 'spread by' text lines added to descriptions. (Ex: Leeched from my stupid BBS!) BOOMLAB will also delete consecutive blank lines this feature is enabled. To delete ALL blank lines use option #7. A sample file 'STRIPDIZ' has been included in this package. The FED/PFED file area manager has an option <CTRL+B> when editing file descriptions, it adds the highlighted line to this file. 9.) List of text strings to REPLACE in DIZ text: Leave blank to disable. One entry per line. Text is not case-sensitive. If the text is found in the DIZ text it is replaced with nothing. Example: BOOMER ----(BOOMER)---- ----()---- 10.) List of characters to translate: Leave blank to disable. BOOMLAB will translate or convert characters found in a description. Enter one character conversion per line and enter in the following format: ß=b A sample 'CONVERT' has been included in this package. 11.) Path\filename of 'Pass-Thru' text to add: This will add your own BBS ad text to the FILE_ID.DIZ or DESC.SDI. All BOOMLAB macros are supported. I don't want to promote use of this I think it's LAME! If you re-process your files a lot locally (FED/PFED) you should put this text or part of it in the 'STRIPDIZ' file (Option #8) so you won't get multiple pass-thru lines. 12.) File with file info text to add to description: Leave blank to disable. Use this option to add archive information and other stats to the file description using BOOMLAB's 30+ different macros. The file can contain however many lines you want but should not exceed the maximum # of spaces allowed per line by your BBS software. The text will be added to the end of any FILE_ID.DIZ or DESC.SDI found. Lines can also be blank and color codes can be used. Example: Line 1> Line 2> @X07Files: |#f, New: |nf, Old: |of Line 3> @X07UL Node |un, Nfo: |nd, Diz: |dd 13.) Text to replace 'Carrier Lost ...' description: <Y/N> - Replaces 'Carrier Lost ...' types descriptions with your own text such as 'WHAT THE HELL IS THIS?' BOOMLAB's macro codes can be used. Replaces: Carrier Lost ... ∞ Description in FILE_ID.DIZ ∞ Contains FILE_ID.DIZ File has a FILE_ID.DIZ 14.) Add 'Uploaded by' string when doing local uploads: <Y/N> 15.) Add 'Uploaded by' string to PCBoard uploads: <Y/N> - BOOMLAB will read the PCBOARD.SYS file & add the Uploaded by text string and uploader name to description. In PCBSETUP under G)Configuration Options, B)File Transfers make sure "Include 'Uploaded by' in desc" is set to 'N'. 16.) 'Uploaded by' text string: Can include color & macro codes. Ex: @X09Uploaded [@X0F|ut@X09] by: @X0F|nm @X09Uploaded [@X0F12:23@X09] by: @X0FBOOMER 17.) PCBoard's PCBALIAS PSA: To enable enter the path to the PCBoard 'USERS' file. Ex: D:\PCB\MAIN\ If a user has entered their alias, this name will be used for 'uploaded by' name. Feature is not available on local uploads. 18.) ULBY.DAT directory: To enable use of ULBY.DAT file, enter it's path. (Ex: C:\PCB\PPE\ULBY\) Do NOT include the ULBY.DAT filename. ULBY.DAT is a database file created by the utility ULBYE100.ZIP by Shawn Reimerdes. BOOMLAB can read this file and if found replace the uploader's name with the alias or special signature the user has added to the ULBY.DAT database file. Ex: @X09Uploaded [@X0F7:50@X09] by: @X0FGene Layton @X09Uploaded [@X0F7:50@X09] by: @X0FB@X07OOMER 19.) Add a blank line between file descriptions: <Y/N> - Gives file DIR a nice, neat appearance. For you anal people out there. FAILED FILE DESCRIPTIONS: ──────────────────────── If a file is failed by BOOMLAB it will put the 'Red Skull' FAILED BOOMLAB message (below) at the beginning of the file description. The regular file description follows it. @X04 ┌───@X0C▄▒▓██▄@X04────────── ─·· · @X30 @X04 │@X0C ░▀████▀█ FAILED BOOMLAB v.62... @X30 @X04 │@X0C ▀▄▄▀▀▄▄▀ ■ F-PROT: VIRUS INFECTED!!! @X30 @X04 │@X0C ▀▀▀▀ ■ α GREEN CATERPILLAR virus @X30 @X04 └──── @X0C▀▀ @X04───── ─·· · · @X30 You can create your own failed BOOMLAB message by creating a file named 'DESCFAIL.MSG' in the BOOMLAB config path. All BOOMLAB macros are supported. A sample can be found in SAMPLES.ZIP. Do not exceed 45 chars per line. ┌─────────────────────────────────┐ │░ 7. VIRUS SCANNING ░░░░░░░░░░░░░│ └─────────────────────────────────┘ Options are listed below in order of their appearance on PAGE #3 of the BOOMLAB configuration program. (BSETUP.EXE) 1.) Virus scanning level: (A=All files, E=Executables ONLY, N=None) 2.) Extensions to bypass when scanning: Those BBS's that allow virus files to be uploaded can list extensions for BOOMLAB not to test. Period must precede extension. Ex: .VIR.NUK 3.) To use RAM-drive enter letter: To enable a RAM-drive for virus scan enter the RAM-Drive letter. This will greatly increase the speed of unpacking and virus scanning of archive files. 4.) Use Heuristic analysis: <Y/N> - Only ThunderByte & F-PROT support heuristic analysis. Use with caution as heuristic virus scans can supposedly find unknown virii but may give a lot of false readings. It requires more memory so it may not be available in local mode. 5.) Quit scanning after virus detected: <Y/N> - When using multiple scanners, 'Y' quits virus scanning after first virus detected. No other scanners are run. If 'N' then all scanners will be run. Running all scanners is desired if your using some of the macros such as |v# and want to report what each scanner found. This option also applies to the <ALT+V> key 'Get Virus Description'. 6.) Virus scanner program used: <1-8> - Select a # corresponding to the virus scanner you are using. McAfee's two SCAN programs use different switches so make sure to select correct program. 1) McAfee's Old Virus Scan SCAN 9.30 V119 2) McAfee's NEW Virus Scan SCAN V2.2.4 3) ThunderByte TBSCAN V6.35 4) Dr. Solomon's FINDVIRU V6.64 5) F-Prot F-PROT V2.18 6) AVScan AVSCAN V2.14 7) AnsiCheck ACHKDIR 8) Norton AntiVirus NAV V2.1 +) Use Multiple Scanners * * You can pass the files through more than just one of the listed scanners if you enter a '+' for scanner #. Enter the scanners under 'MULTIPLE SCANNERS' in BOOMLAB Setup or create a file named SCANNERS.CFG and list the scanners you want to use in the format: Scanner #, Full Path & scanner name. Example: 5,C:\FPROT\F-PROT 3,C:\TB\TBSCAN 2,C:\MCAFEE\SCAN 7.) Scanner path & filename: (Ex: C:\TOOLS\SCAN) Path is not needed if scanner is in the path. Do not include switches. ┌─────────────────────────────────┐ │░ 8. GENERAL/BBS OPTIONS ░░░░░░░░│ └─────────────────────────────────┘ Options are listed below in order of their appearance on PAGE #4 of the BOOMLAB configuration program. (BSETUP.EXE) 1.) Display progress to BBS Users: <Y/N> - If enabled ('Y') BOOMLAB will display to the online user what it is currently doing. Some tests may take some time and the user might think the system is locked and drop carrier. BOOMCOM.EXE and PCBUSER.ANS must be in config file path. (See PCBOARD DISPLAY FILES) 2.) Path\name of privileged user list: To enable enter complete path and filename of a 'privileged user' list file. A privileged user is someone who can upload no wrong. Whenever a file is uploaded by a user named on the privileged user list, the file is passed, no matter how many tests if failed. It is automatically posted but does show all errors in the description to warn users. The format of the file containing the privileged user list is one user name on each line and end each line with a CR/LF. It is NOT case-sensitive and there is no maximum # of names. (PCB only) 3.) List of filenames to blacklist: ASC text file with one filename per line. BOOMLAB will automatically fail any file in this list with 'FILE HAS BEEN BLACKLISTED'. Wildcards accepted. (PCB only) Ex: PFED*.* - Just an example! ;) 4.) Delete uploads without descriptions: <Y/N> - If enabled all uploads without descriptions, either manually entered by user or containing a description file, will be deleted. (PCB only) 5.) Path to move FAILED files to: Leave blank to disable. If a path is entered BOOMLAB will move the failed file to this path. The description will be deleted. Enter 'DELETE' instead of path to delete the file also. (PCB only) NOTE: Leave this option blank to let PCB handle the failed file. PCBoard normally handles failed files by moving the file and it's description to the private uploads directory. 6.) Confirm before a local FAILED file move or delete: <Y/N> - If enabled 'Y' BOOMLAB will prompt 'Confirm (Y/N)?' before moving or deleting files in local mode. (See option #5) 7.) Enable BOOMLAB processing LOG: <Y/N> - If enabled BOOMLAB logs such info a test results, archive info, BBS ads deleted, etc. Logs will be named BOOMLOG.#, where # is the node #. (0=Local) When the size of the LOG exceeds 150k it will start a new LOG renaming the old log 'OLDLOG.#' ┌─────────────────────────────────┐ │░ 9. GIF PROCESSING ░░░░░░░░░░░░░│ └─────────────────────────────────┘ Options are listed below in order of their appearance on PAGE #4 of the BOOMLAB configuration program. (BSETUP.EXE) 1.) Compress GIF's using GIFLITE: <Y/N> - GIFLITE from White River Software compresses uncompressed GIF's about 15-30%. GIFLITE.EXE must be found in same directory or in the path. 2.) GIFLITE command line parameters: (See GIFLITE's docs) Recommended parameters -B -T for don't make a backup of file and use only text graphics. 3.) Process/test GIF's using GIFTEST: <Y/N> - GIFTEST is a shareware GIF utility from Dave Navarro. Features include: > Remove unnecessary extra bytes. > Tests for valid header and complete image. > Check for duplicate upload's. (CRC's) > Define minimum resolutions to accept. > Add resolution to PCBoard descriptions. 4.) GIFTEST command line parameters: (See GIFTEST's docs) NOTE: Resolution values will only be added in standalone mode. Do not use /B: and /F: parameters they will be automatically passed by BOOMLAB. ┌─────────────────────────────────┐ │░ 10. PCBOARD DISPLAY FILES ░░░░░│ └─────────────────────────────────┘ DISPLAYING PROGRESS TO USERS: (PCB ONLY) ──────────────────────────── If 'Display progress to users' is enabled BOOMLAB displays the contents of PCBUSER.ANS at the beginning of each test. It uses the current test macro '|bm'. PCBUSER.ANS and BOOMCOM.EXE must be in BOOMLAB's config path. PCBUSER.ANS is shown below with example of the actual output file. <[19;1H - Ansi code to position display window at line 19. ┌─────────────────────────────────────┐ │ BOOMLAB |vs testing: |fn[12] │ [INPUT] │ ■ |bm[34]│ └─────────────────────────────────────┘ <22;1H - Re-position cursor so it doesn't cause screen to scroll. @X0F┌@X07──@X08─@X07─@X08─────────────────────────────────┐ @X07│ @X0ABOOMLAB v0.62 testing: @X0FBLAB_062.ZIP@X08 │@X30 [OUTPUT] @X08│ @X8F■ @X02Tesing ZIP Integrity @X07│ @X08└─────────────────────────────────@X07─@X08─@X07──@X0F┘ PCBPASS/PCFAIL DISPLAY FILES: (PCB ONLY) ──────────────────────────── After PCBoard returns from the PCBTEST.BAT it looks for files named PCBFAIL.TXT and PCBPASS.TXT. If PCBFAIL.TXT exists then the file failed and it displays the contents of the PCBFAIL.TXT. Otherwise, the file passed and it displays the contents of PCBPASS.TXT. You can customize those screens by using the files PCBPASS.MSG and PCBFAIL.MSG files included in this package. They have to be located in BOOMLAB's config path. You can use all BOOMLAB macro codes to show test results and file information. (See BOOMLAB MACRO CODES) If you don't wish to use them the user will just see PASSED or FAILED. PCBPASS.MSG and PCBUSER.ANS (above) both use the same style graphics as they were designed to be used together. After a file has been tested during a batch upload PCB displays the results from PCBPASS.TXT while PCBUSER.ANS displays the current progress at the bottom of the screen. Did it this way to be a little different. An example of a displayed PCPASS.TXT while BOOMLAB processes the next file follows: @X0F▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄@X70▀@X30 @X0F┌@X07──@X08─@X07─ @X0F█@X7F @X70BOOMLAB v0.62 RESULTS @X08█ ────┐@X30 @X07│ ▀@X08▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ │ @X0F┌@X07──@X08─@X07─@X08───── @X0FFILE STATS @X08──────────┐ @X08│ @X0AFILE TESTED@X08: @X0FBLAB_062.ZIP @X08│ @X07│ @X03type@X08: @X0BPkWare's PKZIP v2.0 @X08│ @X08│ │ │ @X03filesize@X08: @X0B222092 @X08│ @X08│ @X02Archive integrity @X08: @X0APASSED @X08│ │ @X03original@X08: @X0B287880 @X08│ @X08│ @X02Age constraints @X08: @X0APASSED @X08│ │ @X03compression ratio@X08: @X0B24% @X08│ @X08│ @X02ULP Dupe checking @X08: @X0APASSED @X08│ │ @X03total files@X08: @X0B19 @X08│ @X08│ @X02Virus scanned x3 @X08: @X0APASSED @X07│ @X08│ @X03new@X08: @X0B06.20.95 @X03old@X08: @X0B10.17.94 @X08│ @X08└───────────────────────────────@X07─@X08─@X07──@X0F┘ @X08│ @X03diz@X08: @X0B06.13.95 @X03nfo@X08: @X0BNONE @X08│ @X0F┌@X07──@X08─@X07─@X08───────────── @X0FDESCRIPTION @X08─┴─────────────────┐ @X07│ @X07│ @X08│─────────@X07─@X08─@X07──@X0F┘ @X08│ @X07 ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ @X08│ @X08│ @X07■ ▀▄▀▄█▄█▌▌ ≡ BOOMLAB v0.62a ≡ ▐▐█▄█▄▀▄ ▀ ■ @X08│ @X08│ @X07 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ @X08│ @X08│ @X07 COMPLETE Upload Processor for PcBoard. @X08│ @X08│ @X07 Coded by Gene Layton (BOOMER) 06/13/95 @X08│ @X08│ @X07 ° Automated PPE to handle failed files @X08│ @X0F┌@X07──@X08─@X07─@X08─────────────────────────────────┐@X07nt ways. @X08│ @X07│ @X0ABOOMLAB v0.62 testing: @X0FPFED_095.ZIP@X08 │@X08 @X07│ @X08│ @X8F■ @X02Tesing ZIP Integrity @X07│@X08──────────────@X07─@X08─@X07──@X0F┘ @X08└─────────────────────────────────@X07─@X08─@X07──@X0F┘ ┌─────────────────────────────────┐ │░ 11. BOOMLAB MACRO CODES ░░░░░░░│ └─────────────────────────────────┘ Over 30 different BOOMLAB macro codes can be used to personalize BBS Ads, ZIP comments, 'Uploaded by' text, PCB PASS & FAIL files, and add file stats to descriptions. You can format the output by including the length in brackets. Ex: |nm[35] ARCHIVE INFO MACROS: |fn - Filename. |ff - Full path & filename. (To pass to External Utils) |fp - File's path. (To pass to External Utils) |fs - Filesize. |nm - Name of uploader. |nu - Name of uploader. (without any color codes) |nl - New line. (should only use in 'uploaded by' text) |ut - Upload time. |ud - Upload date. |un - Upload node #. |us - Uncompressed size. |cr - Compression ratio. |at - Archive type. Ex: ZIP |ai - Archiver information. Ex: PkWare's PKZIP v1.9 under UNIX |#f - Number of files within archive. |nf - Newest file within archive. |of - Oldest file within archive. |dd - Date of FILE_ID.DIZ. |df - Prints 'φ DIZ' if FILE_ID.DIZ found. |nd - Date of .NFO file. |dz - Contents of FILE_ID.DIZ. Can also add a parameter to limit output Ex: |dz[45,15] = display up to 15 lines. |dw - Same as |dz but stripped of any PCB color codes. DISPLAY FILE MACROS: |vs - BOOMLAB version number. |bm - Current test. For displaying progress. (PCBUSER.ANS) |tv - Virus scan results. |ta - Age test results. |tc - Archive integrity test results. |dt - Type of Dupe checking done. (PCBPASS.MSG) Ex: 'ZDCS Dupe Checking' |td - Dupe Checker results. |vt - Type of virus scanning done. (PCBPASS.MSG) Ex: 'McAfee's 2.1.4 scan' or 'Virus scanned x3' VIRUS INFO MACROS: |vn - Full name of 1st virus found. |va - Names of ALL virus scanner programs used with version #'s. |vp - Name of virus scanner program used. (if using more than one it outputs only 1st) |vv - Version # of the virus scanner in macro |vp. |s# - Scanner name & version of each scanner used. For use with multiple scanner configurations. Ex: |s1: |v1 => McAfee 2.2.2: Found JERUSALEM.1808 virus |s2: |v2 => F-Prot 2.18: Found Jerusalem.1808 Standard |v# - Virus results for each scanner used. For use with multiple scanner configurations. (See also |s#) ┌─────────────────────────────────┐ │░ 12. DELETING BBS ADS ░░░░░░░░░░│ └─────────────────────────────────┘ I'm not a big fan of BBS ads, sometimes a 10K file can grow to over 100k! BOOMLAB offers three ways to locate and kill (ZAP) them: 1.) Configure in BSETUP.EXE (BOOMLAB Setup) a list of filenames (ZAPLIST) to delete when processing archives. Use the <CTRL+B> key in the archive viewer to add new filenames to the list. 2.) Some programs will rename the BBS ad so that method #1 won't be able to locate the filename. However, the CRC value of the file will remain the same if they did not alter the contents. If you add the CRC-32 bit value to the ZAPLIST using the <CTRL+C> key in the archive viewer BOOMLAB should be able to detect it. 3.) While some other programs rename the file AND alter the contents of the BBS ad so even CRC matching won't detect it. Use BSETUP to define a list of text keywords to search for and BOOMLAB will extract all text files and search their contents for any matches. Examples: 'passed through' and 'gigs online' [FOR ZIPS ONLY] A related file you can define in BSETUP is a 'list of files never to be ZAPPED'. Use it if you don't the CRC or text keyword scan to find a file you don't want deleted. ┌─────────────────────────────────┐ │░ 13. FILE SYSOP PPE ░░░░░░░░░░░░│ └─────────────────────────────────┘ FILESYS.PPE is a PPE designed to be used with the BOOMLAB Upload Processor v.54 or higher to automate the handling of failed files. BOOMLAB has four types of tests: CRC, AGE, DUPE & VIRUS. With the FILESYS.PPE you can specify what to do if a file fails any of these tests. You could DELETE a file that failed the CRC test, E-Mail you if a user uploads an old file, NUKE a virus file. All of the options can be used in combination, ex: SYSOP\USER\NUKE would nuke the file and send a message to the sysop and user. Options are: 1) DO NOTHING [NONE] 2) SEND E-MAIL TO SYSOP [SYSOP] 3) SEND E-MAIL TO USER [USER] 4) DELETE FILE [DELETE] 5) NUKE FILE [NUKE] Installation ~~~~~~~~~~~~ 1. Unzip FILESYS.PPE & FILESYS.CFG to the dir where the BOOMLAB.CFG file is located. The path should be the same subdir indicated on the BOOMLAB command line Ex: c:\pcb\pfed\boomlab c:\pcb\pfed\ pcb .... ^^^^^^^^^^ 2. Edit PCBTEXT record 577 (FAILED!) to say (!c:\pcb\pfed\filesys.ppe) or whatever dir your using. 3. Define FILESYS.CFG to your liking. (below) NOTE: If you have problems getting the FILESYS.PPE to work and you have 'Running a Multi-Node System' set to 'N'o. Try setting it to 'Y'es and set the node # to 1. FILESYS.CFG Setup ~~~~~~~~~~~~~~~~~ @x0C ; Color of 'FAILED!' text in PCB BOOMER ; Name to send sysop mail to 1 ; E-Mail Message style YES ; Leave description for nuked file YES ; Leave dummy file (8 bytes) for nuked file DELETE ; Action if file fails Archive test (CRC) 0 ; Archive failure nuke factor (if used) SYSOP ; Action if file fails Age test 5 ; Age test failure nuke factor (if used) SYSOP/USER ; Action if file fails Dupe Check 5 ; Dupe Check failure nuke factor (if used) SYSOP/USER/NUKE ; Action if file fails virus scan 10 ; Virus scan failure nuke factor (if used) *** NOTE: Text must be in ALL CAPS! *** 1. Color of PCB text 'FAILED!' 2. Name to send Sysop E-MAIL to. 3. Message style to use for E-Mail: 1=Red Skull, 2=Blue Box 4. Leave a description for a nuked file. (YES/NO) 5. Leave a dummy file for a nuked file. (YES/NO) Keeps those batch protocols that check paths from uploading same file. It's 8 bytes because if it was a 0 byte PCB would discard it. 6. Action to take for failing Archive Test: NONE = Take no action SYSOP = Send Sysop E-Mail USER = Send User E-Mail DELETE = Deletes file and description. User will not receive any credit. NUKE = Nuke File! - A user can be penalized by factor defined on the next config line (filesize * nukefactor) Can also define whether to leave a description and/or dummy file. (Line #4,5) They can also be used in combination, Ex: NUKE/SYSOP/USER would Nuke the file and send E-Mail to Sysop and the user. Text has to be all caps, combinations separated by a '/'. 7. If using NUKE on archive test failure, set the nuke factor (x bytes) to penalize users. (0=Don't subtract bytes) 8. Action to take for failing Age Test. (See line #6) 9. If using NUKE on age test failure, set the nuke factor (x bytes) to penalize users. (0=Don't subtract bytes) 10. Action to take for failing Dupe Check. (See line #6) 11. If using NUKE on dupe check failure, set the nuke factor (x bytes) to penalize users. (0=Don't subtract bytes) 12. Action to take for failing Virus Scan. (See line #6) 13. If using NUKE on virus scan failure, set the nuke factor (x bytes) to penalize users. (0=Don't subtract bytes) ┌─────────────────────────────────┐ │░ 14. TROUBLE-SHOOTING ░░░░░░░░░░│ └─────────────────────────────────┘ PROBLEM : Files become corrupt after BOOMLAB processes them. SOLUTION: PKZIP/PKUNZIP uses EMS/XMS memory if it can. If there is a shortage of it, the archive can become corrupt. Turn EMS/XMS off using PKCFG.EXE setup. (Tucan Man) PROBLEM: Insufficient memory to run BOOMLAB under PCBoard. SOLUTION: Make sure 'Swap Out During Shell' is enabled. Run PCBSETUP.EXE and select Option G (Configuration Options), then Option D. (Configuration Switches) Set 'Swap Out During Shell' to 'Y'. It will give you about 200K more memory.